Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: switch to any github runner again #859

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

blizzz
Copy link
Member

@blizzz blizzz commented Jun 26, 2024

We had to run integration tests on github runners, as executing on the local ones was unstable some time ago. I understand issues where resolved with local runners, so we can re-enable them again.

  • ⚠️ drop the debug commit before merging ⚠️

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Copy link

@SystemKeeper SystemKeeper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice - yes that was fixed.

@blizzz
Copy link
Member Author

blizzz commented Jun 26, 2024

but all integration tests are red 😬

@SystemKeeper
Copy link

but all integration tests are red 😬

Argh - I only checked the OCI one as that was problematic in the past, but didn't check the integration ones :-S

@blizzz
Copy link
Member Author

blizzz commented Jun 26, 2024

Warning: DOMDocument::loadHTML(): Tag header invalid in Entity, line: 12 in features/bootstrap/FeatureContext.php line 217

It smells as if there is something with the container-container communication

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
@blizzz
Copy link
Member Author

blizzz commented Jun 26, 2024

Warning: DOMDocument::loadHTML(): Tag header invalid in Entity, line: 12 in features/bootstrap/FeatureContext.php line 217

It smells as if there is something with the container-container communication

Warning: DOMDocument::loadHTML(): Tag header invalid in Entity, line: 12 in features/bootstrap/FeatureContext.php line 217

It smells as if there is something with the container-container communication

Water on the mills

Login Failure: Pool is empty and connection creation failed

Edit: but i worked once before, so this is "just" flaky, and probably a race condition somewhere. Could it be that there is not healthcheck polling against the service containers @SystemKeeper ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants